Check-in to checkout systems and methods

ABSTRACT

Provided are check-in to checkout systems and methods. The system includes a point of sale, a display, a mobile device, and a backend system. When the POS starts a transaction, such as, but not limited to scanning an item, the POS generates a transaction/basket identification. In response to starting the transaction, the POS sends the transaction/basket ID to the display in the form of a QR code or one-dimensional barcode. The mobile device operating a mobile application scans and captures the displayed code and reports to the backend systems. The backend systems then send a check-in event, which includes gathered data by the backend systems, to the POS and the POS acknowledges receipt of the message. At this point, a notification may be sent to the mobile application that the check-in was successful and a link is established for flow of information.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/308,473 filed on Nov. 2, 2016 and titled “Check-In to CheckoutSystems and Methods,” which is a '371 national stage patent applicationof International Patent Application No. PCT/US15/55130 filed on Oct. 12,2015 and titled “Check-In to Checkout Systems and Methods,” the entiretyof which are included entirely herein by reference.

FIELD OF THE INVENTION

The invention relates generally to checking out, and more specifically,to systems and methods for checking in at a point of sale system in acheckout area of a store.

BACKGROUND

Merchant point of sale systems can be an inconvenience to the customer.The customers have to wait for all the items to be scanned and totaledbefore facilitating their payment through the merchant's point of salesystems. The customers must also thumb through their wallet to determinewhat form of payment they would like to use for the purchase andswipe/dip the payment instrument for payment. At the end of thetransaction, the customer receives a paper receipt they may need tostore or track for refunds, etc.

BRIEF SUMMARY

In one aspect, provided is a method for checking in at a point of sale.The method comprises: starting a transaction at the point of sale;generating a code in response to starting a transaction at the point ofsale, wherein the code includes a transaction identification; scanningthe code at the point of sale; and associating the transactionidentification with a customer payment profile in response to scanningof the code, wherein payment is effected at the end of the transactionat the point of sale.

In another aspect, provided is a method for checking in at a point ofsale. The method comprises: generating a code for requesting atransaction identification; scanning the code at a point of sale;associating the transaction identification with a customer paymentprofile in response to scanning of the code; and starting a transactionat a point of sale, wherein payment is effected at the end of thetransaction at the point of sale.

In another aspect, provided is a method for checking in at a point ofsale. The method comprises: starting a transaction at the point of sale;generating a transaction identification at the point of sale andproviding it to a wireless device of the point of sale; transmittingdata including the transaction identification from the wireless deviceto a customer mobile device; automatically sending a check-in event fromthe backend systems to the point of sale in response to receiving thetransaction identification from the wireless device; and associating thetransaction identification with a customer payment profile by thebackend system, wherein payment is effected at the end of thetransaction at the point of sale.

In another aspect, provided is a check-in system at a point of sale, thesystem comprising: a point of sale, wherein a transaction identificationis generated at the point of sale; and backend systems, wherein: thetransaction identification is received by the backend systems from oneof the point of sale or a customer mobile device; the backend systemsgather information for associating the transaction identification with acustomer payment profile in response to receiving transactionidentification; and wherein the point of sale communicates with thebackend systems to effect payment at the end of the transaction at thepoint of sale.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The above and further advantages of this invention may be betterunderstood by referring to the following description in conjunction withthe accompanying drawings, in which like numerals indicate likestructural elements and features in various figures. The drawings arenot necessarily to scale, emphasis instead being placed uponillustrating the principles of the invention.

FIG. 1 is a block diagram of a system for re-using e-commerce paymentinstruments for in-store purchasing, in accordance with embodiments.

FIG. 2 is a flow diagram illustrating a method for creating ane-commerce account, in accordance with some embodiments.

FIG. 3 is a flow diagram illustrating a method for setting up e-commercepayments instruments for use in-store, in accordance with someembodiments.

FIG. 4 is an illustrative view of a check-in system, in accordance withsome embodiments.

FIG. 5 is an illustrative view of another check-in system, in accordancewith some embodiments.

FIG. 6 is an illustrative view of yet another check-in system, inaccordance with some embodiments.

FIG. 7 is a flow diagram illustrating a method of pre-requisite steps touse a check-in system, in accordance with embodiments.

FIG. 8 is a flow diagram illustrating a method for checking in at acheckout point of sale, in accordance with embodiments.

FIG. 9 is a flow diagram illustrating another method for checking in ata checkout point of sale, in accordance with embodiments.

FIG. 10 is a flow diagram illustrating yet another method for checkingin at a checkout point of sale, in accordance with embodiments.

DETAILED DESCRIPTION

Many store customers have times when they shop online and other timeswhen they are physically present at a brick-and-mortar store. In orderto shop online, a customer must establish an e-commerce account with theparticular business which often includes entering and storing paymentinstruments in a database for use with the that particular business.This provides ease of checking out at the end of an online shoppingsession, wherein the customer can simply execute a few mouse clicks orother input, such as use of a touchscreen and the like, to executepayment to complete an online transaction. Sometimes the paymentinstruments are stored for future re-use as part of checking out andcompleting an order.

Shopping in a brick-and-mortar store requires the customer must movearound and peruse items and goods with the store, select the goods,often putting them within a cart and then proceeding to a checkout line,where a point of sale terminal is then used to scan or otherwise totalthe amount of money due to purchase the items. The customer must thenretrieve the payment instrument from his or her wallet or purse andprovide the payment instrument to the point of sale terminal. If apayment card is the type of payment instrument, the card is eitherswiped by the customer or the employee at the checkout and the paymentis processed either by entering a personal identification number (“PIN”)or signing to authorize the payment, thus completing the transaction.

Online customers enjoy an expedient check out that is typically notoffered at a brick-and-mortar store. The present inventive conceptsprovide a system and methods for expeditiously processing payment andchecking out with a check-in process that occurs at the beginning of thetransaction taking place at the point of sale. For example, the customercan check-in at the beginning of the process, allowing payment to occurwhen all items are scanned without having to use a physical paymentinstrument.

FIG. 1 is a block diagram of a system 10 for re-using e-commerce paymentinstruments for in-store purchasing. The system 10 may include a backendsystem having various databases, such as, but not limited to useraccounts 14, payment accounts 16, non-payment cards/identifiers 18,payment preferences 20, and payment rules 21. These databases 14, 16, 18and 20 are accessible from an e-commerce application 12. Further, thedatabases 14, 16, 18 and 20 are accessible from a mobile application 22.The system 10 may also include a wallet processor 24, a point of sale(“POS”) 26, a payment gateway 27 and an authorizer(s) 28. The walletprocessor 24 may have access to payments accounts 16, non-paymentcards/identifiers 18, payment preferences 20, and payment rules 21databases. The e-commerce application 12 may be accessible through acomputing device, such as but not limited to a computer, a laptop, atablet, a smartphone and the like. The e-commerce application 12 may bean e-commerce website accessible through an Internet connection. Themobile application 22 may be accessible through a mobile device, such asa smartphone, a tablet and the like. The mobile application 22 may be adownloadable application that is installed and operated on the mobiledevice. The payment gateway 27 may operate to send messages routed tothe authorizers 28.

Referring additionally to FIG. 2, the system 10 may be utilized toexecute a method 30 of creating an e-commerce account. The method 30 mayinclude operating an e-commerce application 12 from a computing device(Step 31); entering user information including customer name, address,user name and password (Step 32); and saving the user information in theuser accounts 14 database (Step 33). The method 30 may further includeentering a payment instrument information through the e-commerceapplication 45 and storing the payment instrument information in thepayment accounts 16 database. The method 30 may also include enteringnon-payment card/identifier information through the e-commerceapplication 12 and storing the non-payment card/identifier informationin the non-payment cards/identifier 18 database. It will be understoodthat the method 30, in some embodiments, is a precondition to using thesystem to complete a transaction at a POS 26.

Further, access to the user accounts 14, payment accounts 16,non-payment cards/identifiers 18 and payment preferences 20 databasesare secured by restricting access to the information. The username andpassword stored in the user accounts 14 database includes theinformation that must be input through a user graphical interface inorder for a customer to login to his or her e-commerce account toaccess, update, change and the like the information stored in the useraccounts 14, payment accounts 16, non-payment cards/identifiers 18, andpayment preferences 20 databases. The customer may login to thee-commerce account through the e-commerce application 12 or through themobile application 22.

It is anticipated that the user account 14 may be changed and updated atany time through use of the e-commerce application 12 or the mobileapplication 22. For example, address information may be updated,additional payment instruments may be added to the payment accounts 16,and additional non-payment cards may be added to the non-paymentcards/identifier 18. Further, as payment instruments expire, the paymentinstrument information stored in the payment accounts 16 may be updatedor removed.

FIG. 3 depicts a method 40 of setting up e-commerce payments instrumentsfor in-store use. For example, the method 40 may include logging intothe e-commerce account (Step 41) through the mobile application 22 orthrough the e-commerce application 12; activating mobile in-storepayment functionality (Step 42), wherein activating the mobile in-storepayment functionality requires creating a new payment authenticationcode, such as a PIN, password and the like; and selecting an existingpayment instrument stored in the payment accounts 16 for use in mobilein-store payment (Step 43). This information may be stored in thepayment preferences 20.

Step 43 of selecting an existing payment instrument may be repeated toselect multiple payment instruments for use with mobile in-storepayments. If multiple payment instruments are selected, the customer mayalso indicate how he or she prefers to use the payment instruments whenconducting transactions in the store.

The method 40 may also include entering a new payment instrument throughthe mobile application 22 and indicating if it may also be used fore-commerce transactions and/or how the customer prefers to use thepayment instrument when transacting in the store.

The method 40 may also include presenting a list of existing non-Paymentcards/identifiers (e.g. Membership, Loyalty, Discount, Offers) to acustomer and selecting which non-payment cards/identifiers to load formobile in-store processing. This may be repeated if there are multiplenon-payment cards on file. The method may also include entering newnon-Payment cards/identifiers to the non-payment cards/identifiers 18database and selecting it to be used for e-commerce transactions or whentransacting in the store.

FIG. 4 depicts a check-in system 110. The system 110 includes a point ofsale (“POS”) 112, a display 114 a and/or a card processing device 114 b,a mobile device 116, and a backend system 120. When the POS 112 starts atransaction, such as, but not limited to scanning an item, the POS 112generates a transaction/basket identification. In response to startingthe transaction, the POS 112 sends the transaction/basket ID to one of acustomer facing display 114 a, a card processing device 114 b or both.The transaction/basket ID may be in the form of a QR code or 1D barcode.A customer uses his or her mobile device 116 operating a mobileapplication 22 to scan and capture the displayed QR code/1D barcode. Themobile application 22 reports to the backend systems 120 that the mobileapplication 22 has captured the transaction/basket ID.

The backend systems 120 operate to gather additional information,determine the specific POS 112 device from the data intransaction/basket ID. The backend systems 120 then sends a check-inevent, which includes the gathered data, to the POS 112. The POS 112acknowledges receipt of the message. At this point, a notification maybe sent to the mobile application 22 that the check-in was successful.Once the check-in is successful, a link is established by the check infor information to flow from the backend systems 120, the mobile device116 and the POS 112, such as, without limitation, payment data,authorizations, customer IDs, basket data, electronic receipts, etc.

FIG. 5 depicts another check-in system 110. The system 110 includes aPOS 112, a scan device 130 of a POS 112, a mobile device 116, and abackend system 120. The mobile device 116 operates a mobile application22 and requests a transaction/basket ID. The mobile application 22 maythen display the transaction/basket ID in the form of a QR code or 1Dbarcode. The scan device 130 of the POS 112 scans the code displayed onthe customer's mobile device 116. The POS 112 reports to backend systems120 that the POS 112 has scanned and captured the transaction/basket ID.

The backend systems 120 operate to gather additional information,determine the specific POS 112 device from the data intransaction/basket ID. The backend systems 120 then send a check-inevent, which includes the gathered data, to the POS 112. The POS 112acknowledges receipt of the message. At this point, a notification maybe sent to the mobile application 22 that the check-in was successful.Once the check-in is successful, a link is established by the check infor information to flow from the backend systems 120, the mobile device116 and the POS 112, such as, without limitation, payment data,authorizations, customer IDs, basket data, electronic receipts, etc.

FIG. 6 depicts yet another check-in system 110. The system 110 includesa point of sale (“POS”) 112, a wireless device 140, a mobile device 116,and a backend systems 120. When the POS 112 starts a transaction, suchas, but not limited to scanning an item, the POS 112 generates atransaction/basket identification. In response to starting thetransaction, the POS 112 sends the transaction/basket ID to the wirelessdevice 140. The wireless device 140 transmits a message containing thetransaction/basket ID. The transmission may be a Bluetooth transmission,a Bluetooth low energy transmission, a near field communicationtransmission, or the like. A customer places his or her mobile device116 within a range or proximity to the wireless device in order todetect the transmission of the message. When the mobile device 116 iswithin range and detects the transmission of the message, the customeris provided with an option to launch a check-in feature. If the customeragrees to the launch the check-in feature, the mobile application 22 islaunched into a check-in mode, wherein the customer may be prompted toenter additional authentication credential. The mobile application 22reports to the backend systems 120 that the mobile application 22 hascaptured the transaction/basket ID.

The backend systems 120 operate to gather additional information,determine the specific POS 112 device from the data intransaction/basket ID. The backend systems 120 then send a check-inevent, which includes the gathered data, to the POS 112. The POS 112acknowledges receipt of the message. At this point, a notification maybe sent to the mobile application 22 that the check-in was successful.Once the check-in is successful, a link is established by the check infor information to flow from the backend systems 120, the mobile device116 and the POS 112, such as, without limitation, payment data,authorizations, customer IDs, basket data, electronic receipts, etc.

In order for the system to operate, some pre-requisite steps must firstbe accomplished as shown in FIG. 7 depicting a method 150 ofpre-requisite steps for using a check-in system. The method 150 mayinclude downloading a mobile application onto a customer device (Step151); creating a login account with authentication credential by thecustomer, wherein the customer has previously logged into the mobileapplication (Step 152); activating a check-in feature and creatingadditional authentication credential (Step 153); and navigating to thecheck-in feature and providing that authentication credential (Step154). In some embodiments, the method 150 may include enabling wirelesscommunications, such as Bluetooth, etc.

FIG. 8 depicts a method 160 for checking in at a point of sale inaccordance with embodiments. The method 160 includes starting atransaction at the point of sale (Step 161); generating a code inresponse to starting a transaction at the point of sale, wherein thecode includes a transaction identification (Step 162); scanning the codeat the point of sale (Step 163); and associating the transactionidentification with a customer payment profile in response to scanningof the code, wherein payment is effected at the end of the transactionat the point of sale (Step 164).

Step 161 of generating the code may comprise generating a QR code orgenerating a one-dimensional code. Step 163 of scanning the code mayinclude scanning the code with a customer mobile device operating amobile application. Scanning of the code with the customer mobile deviceoperating the mobile application transfers the transactionidentification and the customer payment profile to a backend system forassociating the transaction identification with the customer paymentprofile. The code may further include a store identification and aregister identification, as well as additional data to prevent thecontents from being predictable.

The method 160 may further include sending a check-in event the backendsystems to the point of sale for associating the transactionidentification with the customer payment profile, wherein the check-inevent automatically triggers operation of software instruction on thebackend system to associate the transaction identification with thecustomer payment profile.

FIG. 9 depicts a method 170 for checking in at a point of sale inaccordance with embodiments. The method 170 includes generating a codefor requesting a transaction identification (Step 171); scanning thecode at a point of sale (Step 172); associating the transactionidentification with a customer payment profile in response to scanningof the code (Step 173); and starting a transaction at a point of sale,wherein payment is effected at the end of the transaction at the pointof sale (Step 174). According to embodiments, starting a transaction atthe point of sale may occur prior to scanning of the code.

Step 171 of generating the code comprises generating a QR code orgenerating a one-dimensional code. Step 172 of scanning the codeincludes scanning the code with an input device of the point of sale.

The method 170 may further comprising sending a check-in event thebackend systems to the point of sale for associating the transactionidentification with the customer payment profile, wherein the check-inevent automatically triggers operation of software instruction on thebackend system to associate the transaction identification with thecustomer payment profile.

FIG. 10 depicts a method 180 for checking in at a point of sale inaccordance with embodiments. The method 180 includes starting atransaction at the point of sale (Step 181); generating a transactionidentification at the point of sale and providing it to a wirelessdevice of the point of sale (Step 182); transmitting data including thetransaction identification from the wireless device to a customer mobiledevice (Step 183); automatically sending a check-in event from thebackend systems to the point of sale in response to receiving thetransaction identification from the wireless device (Step 184); andassociating the transaction identification with a customer paymentprofile by the backend system, wherein payment is effected at the end ofthe transaction at the point of sale (Step 185).

Step 183 of transmitting data from the wireless device to the customermobile device may include transmitting data with a Bluetooth/Bluetoothlow energy communication, a near field communication, or a radiofrequency communication. The data transmitted from the wireless deviceto the customer mobile device further comprises a store identificationand a register identification.

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method, or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), solid-state drives(SSD), an erasable programmable read-only memory (EPROM or Flashmemory), an optical fiber, a portable compact disc read-only memory(CD-ROM), an optical storage device, a magnetic storage device, or anysuitable combination of the foregoing. In the context of this document,a computer readable storage medium may be any tangible medium that cancontain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wire-line, optical fiber cable, RF, etc., or any suitable combination ofthe foregoing.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a wireless network, a cellulardata network, a local area network (LAN) or a wide area network (WAN),or the connection may be made to an external computer (for example,through the Internet using an Internet Service Provider).

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, cloud-based infrastructurearchitecture, or other devices to cause a series of operational steps tobe performed on the computer, other programmable apparatus or otherdevices to produce a computer implemented process such that theinstructions which execute on the computer or other programmableapparatus provide processes for implementing the functions/actsspecified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

While the invention has been shown and described with reference tospecific preferred embodiments, it should be understood by those skilledin the art that various changes in form and detail may be made thereinwithout departing from the spirit and scope of the invention as definedby the following claims.

What is claimed is:
 1. A check-in system at a point of sale, the systemcomprising: a point of sale in a brick-and-mortar store owned by abusiness, wherein a transaction identification is generated at the pointof sale; and a backend system configured to: receive the transactionidentification by the backend system from a customer mobile device inresponse to scanning a code containing the transaction identification bythe customer mobile device operating a check-in feature of a mobileapplication and providing an authentication credential prior to scanningthe code, wherein the code is generated and at the point of sale anddisplayed on a customer facing display associated with the point ofsale, and wherein the mobile application reports to the backend systemthat the mobile application has captured the transaction identificationin response to scanning the scannable code, prior to completion ofscanning all goods; gather system customer information for associatingthe transaction identification with a customer payment profile of acustomer created e-commerce account for said business in response toreceiving transaction identification and the report from the mobileapplication that captured the transaction identification; and effectpayment at the end of the transaction at the point of sale using atleast one payment instrument stored in the customer created e-commerceaccount for said business, wherein the point of sale is in communicationwith the backend system, wherein the at least one payment instrumenteffects payment for online purchase of goods from said business and forpurchase of goods from the brick-and-mortar store owned by saidbusiness.
 2. The system of claim 1, wherein the code is a QR code. 3.The system of claim 1, wherein backend system sends notifications to thecustomer mobile device when the transaction is completed.
 4. A methodfor checking in at a point of sale, comprising: starting a transactionat the point of sale in a brick-and-mortar store owned by a business inresponse to scanning an item for purchase; generating a scannable codein response to starting the transaction at the point of sale, whereinthe scannable code includes a transaction identification and displayingthe scannable code on a customer facing display coupled to the point ofsale; scanning the code displayed on the customer facing display at thepoint of sale with a customer mobile device operating a check-in featureof a mobile application, wherein scanning the scannable code reports toa backend system that the mobile application has captured thetransaction identification in response to scanning the scannable codeand the backend system determines the specific point of sale deviceassociated with the transaction identification; sending a check-in eventfrom the backend system to the point of sale and the point of saleacknowledging receipt of the check-in event wherein the check-in eventautomatically triggers operation of software instruction on the backendsystem to associate the transaction identification with a customerpayment profile of a customer created e-commerce account for saidbusiness; and effecting payment at the end of the transaction at thepoint of sale using at least one payment instrument stored in thecustomer created e-commerce account for said business, wherein the atleast one payment instrument effects payment for online purchase ofgoods from said business and for purchase of goods from thebrick-and-mortar store owned by said business.
 5. The method of claim 4,wherein generating the code comprises generating a QR code.
 6. Themethod of claim 4, wherein generating the code comprises generating aone-dimensional code.
 7. The method of claim 4, wherein the code furthercomprises a store identification and a register identification.
 8. Amethod for checking in at a point of sale, comprising: generating a codefor requesting a transaction identification and displaying the code on acard processing device coupled to a point of sale in a brick-and-mortarstore owned by a business; scanning the code at the point of saledisplayed on the display with the mobile computing device operating acheck-in feature of a mobile application, wherein scanning the codereports to a backend system that the mobile application has captured thetransaction identification in response to scanning the scannable codeand the backend system determines the specific point of sale deviceassociated with the transaction identification; sending a check-in eventfrom the backend system to the point of sale and the point of saleacknowledging receipt of the check-in event wherein the check-in eventautomatically triggers operation of software instruction on the backendsystem to associate the transaction identification with a customerpayment profile of a customer created e-commerce account for saidbusiness; and starting a transaction at the point of sale in thebrick-and-mortar store owned by said business, effecting payment at theend of the transaction at the point of sale using at least one paymentinstrument of a customer created e-commerce account for said business,wherein the at least one payment instrument effects payment for onlinepurchase of goods from said business and for purchase of goods from thebrick-and-mortar store owned by said business.
 9. The method of claim 8,wherein generating the code comprises generating a QR code.
 10. Themethod of claim 8, wherein generating the code comprises generating aone-dimensional code.
 11. The method of claim 8, wherein scanning thecode comprises scanning the code with an input device of the point ofsale.